Hostname
partex.nu
Last fetched
partex.nu resolves to 3.126.13.38, announced in 3.124.0.0/14 by AMAZON-02 - Amazon.com, Inc. in DE. partex.nu 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
- 3.126.13.38
3.124.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.68.179.212
3.64.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.69.96.114
3.64.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.74.81.10
3.64.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 35.157.220.108
35.156.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.28.120.191
52.28.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 63.181.138.27
63.180.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 63.183.182.57
63.180.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 63.183.177.38
63.180.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for partex.nu is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:2313
Subdomains
| Subdomain |
|---|
| images.partex.nu |
| itsupport.partex.nu |
| markonline.partex.nu |
| media.partex.nu |
| promark.partex.nu |
| static.partex.nu |
| test-partexukproxy.partex.nu |
| test-promark.partex.nu |
| www.partex.nu |
Showing 9 of 9 subdomains (9 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
- ns-39.awsdns-04.com
- ns-682.awsdns-21.net
- ns-1350.awsdns-40.org
- ns-2026.awsdns-61.co.uk
SPF policy
- include: amazonses.com
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from partex.nu 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: "partex.nu"})-[: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.