Hostname
ifs.com
Last fetched
ifs.com resolves to 2 IPv4 addresses operated by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in NL. WHOIS lists iana:146 as the registrar.
Nutrition Label
Resolution chain
ifs.com resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 51.124.7.6 | 51.124.0.0/16 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | NL |
| 64.239.109.1 | 64.239.109.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:146
- Organization
- domain administrator
- Contact emails
Subdomains
106 observed subdomains of ifs.com.
Showing 25 of 106. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from ifs.com in the public web crawl.
1,440 sites link to this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
29 SPF mechanisms authorising senders for ifs.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | 146014973.spf04.hubspotemail.net |
| SPF_INCLUDE | _spf.salesforce.com |
| SPF_INCLUDE | mandrillapp.com |
| SPF_INCLUDE | md02.com |
| SPF_INCLUDE | mktomail.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 149.96.51.126 |
| SPF_IP | 149.96.67.126 |
| SPF_IP | 167.89.73.249/32 |
| SPF_IP | 176.28.48.67 |
| SPF_IP | 185.84.1.202/32 |
| SPF_IP | 189.36.2.51 |
| SPF_IP | 192.237.158.85/32 |
| SPF_IP | 193.41.170.218 |
| SPF_IP | 193.41.170.219 |
| SPF_IP | 193.41.170.220 |
| SPF_IP | 199.127.232.0/22 |
| SPF_IP | 199.255.192.0/22 |
| SPF_IP | 199.91.137.20/32 |
| SPF_IP | 199.91.137.22/32 |
| SPF_IP | 199.91.137.8/29 |
| SPF_IP | 23.253.182.234/32 |
| SPF_IP | 37.98.232.20/32 |
| SPF_IP | 37.98.232.22/32 |
| SPF_IP | 37.98.232.8/29 |
| SPF_IP | 40.71.35.61 |
| SPF_IP | 54.240.0.0/18 |
| SPF_IP | 69.169.224.0/20 |
| SPF_IP | 80.82.206.14 |
Related pages
Pivot deeper into the graph from ifs.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "ifs.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.