tinflag.com - dns.ninja
tinflag.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=1785242407 | ||||||
Same first word
tinflag.com |
Similar names
falting.com |
fgatlin.com |
langfit.de |
ftliang.com |
flating.com |
tlifang.com |
gnalift.com.tr |
giftlan.com |
latingf.com |
tlifang.net |
langfit.net |
gnalift.com |
intflag.com |
langfit.com |
flating.ru |
filtang.com |
DNS History
9 records (7 active, 2 former)
●NSdns1.registrar-servers.com2026-07-08 → 2026-07-28 · 3 obs
● 2026-07-08 20:38:12
● 2026-07-28 13:02:10
●NSdns2.registrar-servers.com2026-07-08 → 2026-07-28 · 3 obs
● 2026-07-08 20:38:12
● 2026-07-28 13:02:10
○NSns55.worldnic.com2015-08-22 → 2017-04-05 · 4 obs
● 2017-04-05 07:17:40
○ 2026-07-08 20:38:12
○ 2026-07-28 13:02:10
○NSns56.worldnic.com2015-08-22 → 2017-04-05 · 4 obs
● 2017-04-05 07:17:40
○ 2026-07-08 20:38:12
○ 2026-07-28 13:02:10
●MXalt1.aspmx.l.google.com2015-08-22 → 2026-07-28 · 2 obs
● 2026-07-28 13:02:10
●MXalt2.aspmx.l.google.com2015-08-22 → 2026-07-28 · 2 obs
● 2026-07-28 13:02:10
●MXaspmx.l.google.com2015-08-22 → 2026-07-28 · 2 obs
● 2026-07-28 13:02:10
●MXaspmx2.googlemail.com2015-08-22 → 2026-07-28 · 2 obs
● 2026-07-28 13:02:10
●MXaspmx3.googlemail.com2015-08-22 → 2026-07-28 · 2 obs
● 2026-07-28 13:02:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| tinflag.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.132.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 187ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)
Analysis
Name Servers
tinflag.com is served by two delegated name servers, dns1.registrar-servers.com and dns2.registrar-servers.com.
tinflag.com shares its NS records with other domains, for example ilocosempanada.com, hzcsa.xyz, freshnewsflow.com and two others.
tinflag.com and other domains like nwlane.com, memery.info and emiba.org share some name servers
These name servers are frequently paired with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.
Each of the two host names carries two IP addresses: dns1.registrar-servers.com points to 156.154.132.200 and 2610:a1:1024::200, and dns2.registrar-servers.com points to 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
tinflag.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 tinflag.com and other domains, including ns500754.ns500742.ns500754.ns500671.ns500754.ns500688.ns500704.ns500291.ns500291.ns500666.tenderladiesbz.com, ns500759.ns500698.ns500759.ns500698.ns500736.ns500736.ns500735.ns500735.ns500698.ns500698.ns500698.ns500698.ns500708.ns500619.ns500698.ns500652.ns500576.trackreceptor.com, ns500758.ns500698.ns500758.ns500698.ns500698.ns500735.ns500736.ns500736.ns500736.ns500698.ns500708.ns500698.trackreceptor.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 maps to two IP addresses — 108.177.123.26 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com maps to two IP addresses — 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com maps to two IP addresses — 173.194.45.26 and 2607:f8b0:4004:c1f::1a.
alt1.aspmx.l.google.com maps to two IP addresses — 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.26 and 2a00:1450:400b:c02::1a.
These two host names — aspmx2.googlemail.com and alt1.aspmx.l.google.com — each point to 2800:3f0:4003:c0f::1b IP addresses.
These two host names — aspmx3.googlemail.com and alt2.aspmx.l.google.com — each point to 2a00:1450:400b:c02::1a IP addresses.
These two host names — aspmx3.googlemail.com and alt2.aspmx.l.google.com — each point to 172.253.116.26 IP addresses.