Hostname
upig.de
Last fetched
upig.de resolves to 104.79.33.118, announced in 104.79.32.0/20 by AKAMAI-AS - Akamai Technologies, Inc. in DE. upig.de is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.79.33.118
104.79.32.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Berlin, DE
- 23.203.180.154
23.203.176.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · New York, US
- 23.215.21.240
23.215.16.0/21 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.45.104.107
23.45.96.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.56.206.236
23.56.200.0/21 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for upig.de is recorded in WhisperGraph.
Attribution
akamai
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for upig.de. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
| Subdomain |
|---|
| api.upig.de |
| www.upig.de |
Showing 2 of 2 subdomains (2 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- a1-27.akam.net
- a10-64.akam.net
- a16-64.akam.net
- a28-64.akam.net
- a3-67.akam.net
- a9-65.akam.net
MX records
- mxa-00176a04.gslb.pphosted.com
- mxb-00176a04.gslb.pphosted.com
- mx0a-00176a04.pphosted.com
- mx0b-00176a04.pphosted.com
SPF policy
- include: %{ir}.%{v}.%{d}.spf.has.pphosted.com
Threat-feed evidence
History
Related pages
Pivot from upig.de 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: "upig.de"})-[: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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.