Hostname
4frontes.com
Last fetched
4frontes.com resolves to 3 IPv4 addresses operated by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US. WHOIS lists iana:299 as the registrar.
Nutrition Label
Resolution chain
4frontes.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 |
|---|---|---|---|---|
| 51.143.107.76 | 51.140.0.0/14 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | US |
| 52.137.90.183 | 52.136.0.0/13 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | US |
| 52.156.93.30 | 52.152.0.0/13 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | US |
WHOIS identity
- Registrar
- iana:299
- Organization
- 4front engineered solutions,
- Contact emails
Subdomains
21 observed subdomains of 4frontes.com.
Showing 20 of 21. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from 4frontes.com in the public web crawl.
31 sites link to this hostname.
Sample inbound links
Sample outbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
10 SPF mechanisms authorising senders for 4frontes.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | dedicated.mysmtp.com |
| SPF_INCLUDE | em9751.4frontes.com |
| SPF_INCLUDE | emailus.freshservice.com |
| SPF_INCLUDE | sendgrid.net |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 141.81.167.228 |
| SPF_IP | 35.214.183.81/32 |
| SPF_IP | 35.214.208.81/32 |
| SPF_IP | 35.214.212.238/32 |
| SPF_IP | 35.214.213.218/32 |
Related pages
Pivot deeper into the graph from 4frontes.com.
- IP · 51.143.107.76
- ASN · AS8075MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation
- Registrar · iana:299
- Country · US
- Email · domain.aaes@assaabloy.com
- TLD · .com
- Browse hostnames · 4f…
- 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: "4frontes.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.