Hostname
levi.com
Last fetched
levi.com resolves to 10 IPv4 addresses operated by AKAMAI-AS - Akamai Technologies, Inc. in NL.
Nutrition Label
Resolution chain
levi.com resolves to 10 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 184.30.157.40 | 184.30.156.0/22 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | NL |
| 23.193.237.49 | 23.193.236.0/22 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | NL |
| 23.209.209.64 | 23.209.208.0/22 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | DE |
| 23.220.112.246 | 23.220.112.0/22 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | NL |
| 23.36.21.45 | 23.36.20.0/22 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | US |
| 23.51.60.252 | 23.51.60.0/22 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | JP |
| 23.62.105.57 | 23.62.104.0/23 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | US |
| 72.246.28.139 | 72.246.28.0/22 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | DE |
| 88.221.168.144 | 88.221.168.0/22 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | DE |
| 23.52.180.243 | 23.52.180.0/22 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | DE |
WHOIS identity
WHOIS data is temporarily unavailable. Refresh in a moment to retry.
Subdomains
Subdomain count is temporarily unavailable. Refresh in a moment to retry.
Web-graph footprint
Distinct hostnames that link to or from levi.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
7 SPF mechanisms authorising senders for levi.com.
| Mechanism | Target |
|---|---|
| SPF_A | b.spf.service-now.com |
| SPF_A | c.spf.service-now.com |
| SPF_A | d.spf.service-now.com |
| SPF_INCLUDE | mail.zendesk.com |
| SPF_INCLUDE | spf-003beb01.pphosted.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_INCLUDE | spf.servicemail24.de |
Related pages
Pivot deeper into the graph from levi.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "levi.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.