sfsave.com
Its Domain Power Rank is relatively low.
- Global Rank
- #11,912,282
▼ 1,719,493
- Rank in TLD
- #5,141,289
▼ 787,018
- Referring Domains
- 2
▼ 1
- Avg. Referrer Power Rank
- 37.1
- Subdomains
- 1
- Domain age
- 5 yr 0 mo
Link Overview
- Avg. Referrer Power Rank
- 37.1
- Median Referrer Power Rank
- 37.1
- Referring Domains
- 2
- Linked Domains
- 12
Referring Domains by Power Rank
0–9 1
10–19 0
20–29 0
30–39 0
40–49 0
50–59 0
60–69 0
70–79 1
80–89 0
90–100 0
Total 2
Referring Domains
| Referring domain | Power Rank | Global Rank |
|---|---|---|
| statefarm.com | 73.6 | #1,687 |
| sfinsman.com | 0.5 | #135,054,481 |
Basic Information
- TLD
- .com
- Registration date
- 4 Nov 2021
- Last updated
- 4 Oct 2026
- Expires
- 4 Nov 2027 (364 days remaining)
- Domain statuses
- clientTransferProhibited
- Registry
- VeriSign Global Registry Services
- Registrar
- GANDI SAS
Subdomain
www.sfsave.com
DNS
| Type | Name | TTL | Value |
|---|---|---|---|
| A | sfsave.com | 300 | 34.69.219.172 |
| MX | sfsave.com | 300 | 2 newman-nyc-do.mirus.io |
| MX | sfsave.com | 300 | 1 newman-dfw-lin.mirus.io |
| NS | sfsave.com | 300 | ns-cloud-b4.googledomains.com |
| NS | sfsave.com | 300 | ns-cloud-b3.googledomains.com |
| NS | sfsave.com | 300 | ns2.mir.us |
| NS | sfsave.com | 300 | ns-cloud-b1.googledomains.com |
| NS | sfsave.com | 300 | ns-cloud-b2.googledomains.com |
| NS | sfsave.com | 300 | ns1.mirusresearch.com |
| SOA | sfsave.com | 21600 | ns-cloud-b1.googledomains.com. cloud-dns-hostmaster.google.com. 1 21600 3600 259200 300 |
| TXT | sfsave.com | 300 | v=spf1 +a +mx +include:spf.mtasv.net -all |
| TXT | sfsave.com | 300 | google-site-verification=U32Q93hHxzGfyUFfn2BQ_3QDp0SgK9uCRcyH8awVTls |
Email Authentication
- MX
- Valid
- SPF
- Valid
- DMARC
- Valid
DMARC is set to p=reject, asking receiving servers to reject messages that fail authentication.
Some information is cached or comes from our own analysis, so it may not be current or complete. Our link analysis does not cover every link on the web. Metrics are based on our own methodology and should not be taken as definitive assessments of a domain’s or service’s quality or trustworthiness.