Skip to content

Hostname

flightdocs.com

Last fetched

flightdocs.com resolves to 199.60.103.66, announced in 199.60.103.0/24 by CLOUDFLARESPECTRUM - Cloudflare London, LLC in US. flightdocs.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · flightdocs.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/flightdocs.com

Resolution chain

IPv6 resolution

No AAAA record for flightdocs.com is recorded in WhisperGraph.

Attribution

cloudflare london

ORIGIN_AS

WHOIS identity

Registrar
iana:9
Registrant organisation
perfect privacy,
Contact emails
02ba725c0a28fd0a3494aef82900ca0c@domaindiscreet.com, 6f2ff6c10a28fd0a0918c97007bc571a@domaindiscreet.com, ac92753d0a28fd0a6aac6b2cb14bb56a@domaindiscreet.com, baf169e30a28fd0a41d50eb6fcfda1fd@domaindiscreet.com, d43f3e6f0a28fd0a39ac5cee5bdda11c@domaindiscreet.com, ffpmuqgstojfua101k8a5npbc2@domaindiscreet.com, uj8em42u9gr@networksolutionsprivateregistration.com

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns-349.awsdns-43.com
  • ns-626.awsdns-14.net
  • ns-1397.awsdns-46.org
  • ns-1785.awsdns-31.co.uk

MX records

  • flightdocs-com.mail.protection.outlook.com

SPF policy

  • include: _spf.intacct.com
  • include: spf.mandrillapp.com
  • include: spf.protection.outlook.com
  • include: _spf.salesforce.com
  • include: 4078465.spf03.hubspotemail.net
  • include: sendgrid.net
  • ip: 199.231.170.29
  • ip: 204.98.53.85

Threat-feed evidence

History

Related pages

Pivot from flightdocs.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "flightdocs.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.