inglify.com - dns.ninja
inglify.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| NS | ns1.afternic.com ⭐ | ||||||
| NS | ns2.afternic.com | ||||||
| A | 2603:5:2226::45🇺🇸 GODADDY-DNS2603:5:2220::/44 | ||||||
| PTR | ns2.afternic.com | ||||||
| A | 173.201.66.69🇺🇸 GODADDY-DNS173.201.66.0/23 | ||||||
| PTR | ns2.afternic.com | ||||||
| NS | verification-d3jclucsp89ganyqbydeny.ns101.verify.hn ⚠️ Not in zone NS records | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns1.afternic.comdns@jomax.net serial=1 | ||||||
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=1783044791 | ||||||
Same first word
inglify.com |
Similar names
iflying.com.cn |
flyingi.net |
iflying.me |
lignify.com |
iflying.com |
fliying.com |
flyingi.com |
lingify.net |
filying.com |
DNS History
9 records (5 active, 4 former)
○NSns-cloud-a1.googledomains.com2020-01-28 → 2020-01-28 · 3 obs
○ 2026-03-21 08:54:00
○ 2026-07-03 02:15:54
○NSns-cloud-a2.googledomains.com2020-01-28 → 2020-01-28 · 3 obs
○ 2026-03-21 08:54:00
○ 2026-07-03 02:15:54
○NSns-cloud-a3.googledomains.com2020-01-28 → 2020-01-28 · 3 obs
○ 2026-03-21 08:54:00
○ 2026-07-03 02:15:54
○NSns-cloud-a4.googledomains.com2020-01-28 → 2020-01-28 · 3 obs
○ 2026-03-21 08:54:00
○ 2026-07-03 02:15:54
●NSns1.afternic.com2026-03-21 → 2026-07-03 · 3 obs
● 2026-03-21 08:54:00
● 2026-07-03 02:15:54
●NSns2.afternic.com2026-03-21 → 2026-07-03 · 3 obs
● 2026-03-21 08:54:00
● 2026-07-03 02:15:54
●NSverification-d3jclucsp89ganyqbydeny.ns101.verify.hn2026-03-21 → 2026-07-03 · 3 obs
● 2026-03-21 08:54:00
● 2026-07-03 02:15:54
●A13.248.169.482026-03-21 → 2026-07-03 · 2 obs
● 2026-07-03 02:15:54
●A76.223.54.1462026-03-21 → 2026-07-03 · 2 obs
● 2026-07-03 02:15:54
🔍 DNS Trace
Analysis
IP Addresses
inglify.com points to the IP addresses 13.248.169.48 and 76.223.54.146
Two other host names, along with u-translate.com, canaryfair.com and floridaeventplanning.com, also share IP numbers with inglify.com.
Name Servers
inglify.com is delegated to three name servers: ns1.afternic.com, ns2.afternic.com and verification-d3jclucsp89ganyqbydeny.ns101.verify.hn.
There is at least partial name server overlap between inglify.com and other domains — activgen.com, lader.org, mrm.tech and two more among them.
These name servers are routinely deployed together with the name servers verification-iryqusbri9xlks4ssi7d4w.ns101.verify.hn.
ns2.afternic.com and verification-d3jclucsp89ganyqbydeny.ns101.verify.hn each resolve to two IP addresses: ns2.afternic.com points to 173.201.66.69 and 2603:5:2226::45, while verification-d3jclucsp89ganyqbydeny.ns101.verify.hn points to 13.248.169.48 and 76.223.54.146.