flightrequest.com - dns.ninja

flightrequest.com

com

Previously MX for

Subdomains

Same first word

DNS History

23 records (4 active, 19 former)

200920112013201520172019202120232025NSns1.afternic.comns2.afternic.comns1.dsredirection.comns1.kualo.netns1.namebrightdns.comns2.dsredirection.comns2.kualo.netns2.namebrightdns.comns3.kualo.netns4.kualo.netMXflightrequest.commail1.filteredmx.netmail2.filteredmx.netmail3.filteredmx.netA13.248.169.4876.223.54.146208.73.212.1234.194.81.22450.115.18.1050.115.18.2854.210.39.6691.197.229.64CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com
●NSns1.afternic.com2026-04-24 β†’ 2026-06-21 Β· 3 obs
β—‹ 2017-05-20 02:00:00
● 2026-04-24 13:15:28
● 2026-06-21 13:50:18
β—‹NSns1.dsredirection.com2008-03-19 β†’ 2008-03-19 Β· 3 obs
● 2008-03-19 19:59:54
β—‹ 2015-05-31 07:27:44
β—‹ 2026-06-21 13:50:18
β—‹NSns1.kualo.net2015-05-31 β†’ 2016-03-31 Β· 5 obs
β—‹ 2008-03-19 19:59:54
● 2015-05-31 07:27:44
● 2016-03-31 10:16:36
β—‹ 2017-05-20 02:00:00
β—‹ 2026-06-21 13:50:18
β—‹NSns1.namebrightdns.com2017-05-20 β†’ 2017-05-20 Β· 4 obs
β—‹ 2016-03-31 10:16:36
● 2017-05-20 02:00:00
β—‹ 2026-04-24 13:15:28
β—‹ 2026-06-21 13:50:18
●NSns2.afternic.com2026-04-24 β†’ 2026-06-21 Β· 3 obs
β—‹ 2017-05-20 02:00:00
● 2026-04-24 13:15:28
● 2026-06-21 13:50:18
β—‹NSns2.dsredirection.com2008-03-19 β†’ 2008-03-19 Β· 3 obs
● 2008-03-19 19:59:54
β—‹ 2015-05-31 07:27:44
β—‹ 2026-06-21 13:50:18
β—‹NSns2.kualo.net2015-05-31 β†’ 2016-03-31 Β· 5 obs
β—‹ 2008-03-19 19:59:54
● 2015-05-31 07:27:44
● 2016-03-31 10:16:36
β—‹ 2017-05-20 02:00:00
β—‹ 2026-06-21 13:50:18
β—‹NSns2.namebrightdns.com2017-05-20 β†’ 2017-05-20 Β· 4 obs
β—‹ 2016-03-31 10:16:36
● 2017-05-20 02:00:00
β—‹ 2026-04-24 13:15:28
β—‹ 2026-06-21 13:50:18
β—‹NSns3.kualo.net2015-05-31 β†’ 2016-03-31 Β· 5 obs
β—‹ 2008-03-19 19:59:54
● 2015-05-31 07:27:44
● 2016-03-31 10:16:36
β—‹ 2017-05-20 02:00:00
β—‹ 2026-06-21 13:50:18
β—‹NSns4.kualo.net2015-05-31 β†’ 2016-03-31 Β· 5 obs
β—‹ 2008-03-19 19:59:54
● 2015-05-31 07:27:44
● 2016-03-31 10:16:36
β—‹ 2017-05-20 02:00:00
β—‹ 2026-06-21 13:50:18
β—‹MXflightrequest.com2015-05-31 β†’ 2016-03-31 Β· 7 obs
β—‹ 2008-03-19 19:59:54
● 2015-05-31 07:27:44
β—‹ 2015-10-21 19:07:24
● 2016-01-04 07:32:02
● 2016-03-31 10:16:36
β—‹ 2017-05-20 02:00:00
β—‹ 2026-06-21 13:50:18
β—‹MXmail1.filteredmx.net2015-10-21 β†’ 2015-10-21 Β· 4 obs
β—‹ 2015-05-31 07:27:44
● 2015-10-21 19:07:24
β—‹ 2016-01-04 07:32:02
β—‹ 2026-06-21 13:50:18
β—‹MXmail2.filteredmx.net2015-10-21 β†’ 2015-10-21 Β· 4 obs
β—‹ 2015-05-31 07:27:44
● 2015-10-21 19:07:24
β—‹ 2016-01-04 07:32:02
β—‹ 2026-06-21 13:50:18
β—‹MXmail3.filteredmx.net2015-10-21 β†’ 2015-10-21 Β· 4 obs
β—‹ 2015-05-31 07:27:44
● 2015-10-21 19:07:24
β—‹ 2016-01-04 07:32:02
β—‹ 2026-06-21 13:50:18
●A13.248.169.482026-04-24 β†’ 2026-06-21 Β· 3 obs
β—‹ 2017-05-20 02:00:00
● 2026-04-24 13:15:28
● 2026-06-21 13:50:18
β—‹A208.73.212.122008-03-19 β†’ 2008-03-19 Β· 3 obs
● 2008-03-19 19:59:54
β—‹ 2015-05-31 07:27:44
β—‹ 2026-06-21 13:50:18
β—‹A34.194.81.2242017-05-20 β†’ 2017-05-20 Β· 4 obs
β—‹ 2016-03-31 10:16:36
● 2017-05-20 02:00:00
β—‹ 2026-04-24 13:15:28
β—‹ 2026-06-21 13:50:18
β—‹A50.115.18.102015-05-31 β†’ 2015-05-31 Β· 4 obs
β—‹ 2008-03-19 19:59:54
● 2015-05-31 07:27:44
β—‹ 2015-10-21 19:07:24
β—‹ 2026-06-21 13:50:18
β—‹A50.115.18.282015-10-21 β†’ 2015-10-21 Β· 4 obs
β—‹ 2015-05-31 07:27:44
● 2015-10-21 19:07:24
β—‹ 2016-01-04 07:32:02
β—‹ 2026-06-21 13:50:18
β—‹A54.210.39.662017-05-20 β†’ 2017-05-20 Β· 4 obs
β—‹ 2016-03-31 10:16:36
● 2017-05-20 02:00:00
β—‹ 2026-04-24 13:15:28
β—‹ 2026-06-21 13:50:18
●A76.223.54.1462026-04-24 β†’ 2026-06-21 Β· 3 obs
β—‹ 2017-05-20 02:00:00
● 2026-04-24 13:15:28
● 2026-06-21 13:50:18
β—‹A91.197.229.642016-01-04 β†’ 2016-03-31 Β· 5 obs
β—‹ 2015-10-21 19:07:24
● 2016-01-04 07:32:02
● 2016-03-31 10:16:36
β—‹ 2017-05-20 02:00:00
β—‹ 2026-06-21 13:50:18
β—‹CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-05-20 β†’ 2017-05-20 Β· 3 obs
● 2017-05-20 02:00:00
β—‹ 2026-04-24 13:15:28
β—‹ 2026-06-21 13:50:18

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
comc.gtld-servers.net, m.gtld-servers.net, k.gtld-servers.net, a.gtld-servers.net...-
flightrequest.comns1.afternic.com, ns2.afternic.com4 records

βœ… Authoritative Response

Server:97.74.98.69

NS records: ns1.afternic.com, ns2.afternic.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for flightrequest.com (unsigned zone)

⏱️ Timing

Total: 1436ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A276.223.54.146, 13.248.169.48
NS2ns1.afternic.com, ns2.afternic.com
MX1. (pri: 0)
TXT1v=spf1 -all
SOA1ns1.afternic.com dns.jomax.net

πŸ“Œ Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)

Analysis

Hierarchy

The domain fli.flightrequest.com falls under the parent flightrequest.com.

IP Addresses

flightrequest.com has two IP addresses: 13.248.169.48 and 76.223.54.146

Among the host names that share IP numbers with flightrequest.com are trendkorea.com, compandy.com, shala.pt and two others.

Name Servers

flightrequest.com is served by two delegated name servers, ns1.afternic.com and ns2.afternic.com.

flightrequest.com has the same name server delegation as a number of other domains, such as mail.zenmartin.com, vv94.com, charmnow.com and two more.

At least some of flightrequest.com's name servers are shared with other domains, for example surffers.com, frawal.com, sacuv.com and two more.

These name servers tend to be deployed in combination with the name servers verification-d3jclucsp89ganyqbydeny.ns101.verify.hn and verification-urj2ap2akmgcchkhharttb.ns101.verify.hn.

Each of the two host names carries two IP addresses: ns1.afternic.com points to 97.74.98.69 and 2603:5:2126::45, and ns2.afternic.com points to 173.201.66.69 and 2603:5:2226::45.