Hostname
guardianflight.com
Last fetched
guardianflight.com resolves to 3 IPv4 addresses operated by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in CA. WHOIS lists iana:3786 as the registrar.
Nutrition Label
Resolution chain
guardianflight.com resolves to 3 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 13.107.213.41 | 13.104.0.0/14 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | CA |
| 13.107.246.41 | 13.104.0.0/14 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | CA |
| 150.171.109.147 | 150.171.0.0/16 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | KE |
WHOIS identity
- Registrar
- iana:3786
- Organization
- air medical group holdings,
- Contact emails
Subdomains
3 observed subdomains of guardianflight.com.
Web-graph footprint
Distinct hostnames that link to or from guardianflight.com in the public web crawl.
37 sites link to this hostname.
24 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
11 SPF mechanisms authorising senders for guardianflight.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_INCLUDE | spf.smtp2go.com |
| SPF_INCLUDE | us._netblocks.mimecast.com |
| SPF_IP | 107.189.102.85 |
| SPF_IP | 199.96.142.13 |
| SPF_IP | 199.96.142.14 |
| SPF_IP | 209.132.193.6 |
| SPF_IP | 40.113.192.211 |
| SPF_IP | 64.49.231.39 |
| SPF_IP | 65.215.163.251 |
| SPF_IP | 65.215.163.252 |
Related pages
Pivot deeper into the graph from guardianflight.com.
- IP · 13.107.213.41
- ASN · AS8075MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation
- Registrar · iana:3786
- Country · CA
- Email · chrisgebhardt@amrg.com
- TLD · .com
- Browse hostnames · gu…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "guardianflight.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.