rfcf.com - dns.ninja
rfcf.com
com
| DNSSEC | ๐ Signed (DS record present) | ||||||
| NS | a.gtld-servers.net โญ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1781359438 | ||||||
Same first word
Similar names
DNS History
10 records (9 active, 1 former)
โNSns19.domaincontrol.com2015-06-25 โ 2026-06-13 ยท 2 obs
โ 2026-06-13 14:19:50
โNSns20.domaincontrol.com2015-06-25 โ 2026-06-13 ยท 2 obs
โ 2026-06-13 14:19:50
โMXalt1.aspmx.l.google.com2015-06-25 โ 2026-06-13 ยท 2 obs
โ 2026-06-13 14:19:50
โMXalt2.aspmx.l.google.com2015-06-25 โ 2026-06-13 ยท 2 obs
โ 2026-06-13 14:19:50
โMXaspmx.l.google.com2015-06-25 โ 2026-06-13 ยท 2 obs
โ 2026-06-13 14:19:50
โMXaspmx2.googlemail.com2015-06-25 โ 2026-06-13 ยท 2 obs
โ 2026-06-13 14:19:50
โMXaspmx3.googlemail.com2015-06-25 โ 2026-06-13 ยท 2 obs
โ 2026-06-13 14:19:50
โA15.197.148.332026-02-19 โ 2026-06-13 ยท 3 obs
โ 2026-02-19 07:46:30
โ 2026-06-13 14:19:50
โA3.33.130.1902026-02-19 โ 2026-06-13 ยท 3 obs
โ 2026-02-19 07:46:30
โ 2026-06-13 14:19:50
โA50.63.202.622015-06-25 โ 2018-06-12 ยท 4 obs
โ 2018-06-12 09:52:10
โ 2026-02-19 07:46:30
โ 2026-06-13 14:19:50
๐ DNS Trace
๐ Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | e.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, b.gtld-servers.net... | - |
| rfcf.com | ns19.domaincontrol.com, ns20.domaincontrol.com | 4 records |
โ Authoritative Response
Server:97.74.109.10
NS records: ns19.domaincontrol.com, ns20.domaincontrol.com
๐ DNSSEC Status
โ ๏ธ Insecure (no DNSSEC)
No DS record for rfcf.com (unsigned zone)
โฑ๏ธ Timing
Total: 153ms | Queries: -
๐ Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 3.33.130.190, 15.197.148.33 |
| NS | 2 | ns19.domaincontrol.com, ns20.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 20), alt2.aspmx.l.google.com (pri: 30)... |
| SOA | 1 | ns19.domaincontrol.com dns.jomax.net |
๐ Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns19.domaincontrol.com, ns19.domaincontrol.com, ns20.domaincontrol.com...)
Analysis
IP Addresses
rfcf.com points to two IP numbers: 3.33.130.190 and 15.197.148.33.
Two other host names, along with torasi.com, buzzyby.com and mestrain.com, also share IP numbers with rfcf.com.
Name Servers
rfcf.com uses two name servers for its delegation: ns19.domaincontrol.com and ns20.domaincontrol.com.
rfcf.com shares its NS records with other domains, for example couponsnoop.com, pointpcs.com, alrig.com and two others.
The two host names ns19.domaincontrol.com and ns20.domaincontrol.com each have a pair of IP addresses: ns19.domaincontrol.com has 97.74.109.10 and 2603:5:21d0::a, and ns20.domaincontrol.com has 173.201.77.10 and 2603:5:22d0::a.
Mail Servers
rfcf.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between rfcf.com and other domains, including jtsl.pt, ns500698.ns500759.ns500759.ns500698.ns500736.ns500698.ns500698.ns500736.ns500735.ns500735.ns500708.ns500652.ns500619.ns500619.trackreceptor.com, ns500699.ns500734.ns500734.ns500734.ns500699.ns500693.ns500683.ns500588.ns500683.ns500683.ns500699.ns500683.ns500612.ns500612.ns500110.dtrkdll.com and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 173.194.45.27 and 2607:f8b0:4004:c23::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1a IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.26 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1a IP addresses each.