Hostname
nr.bidderstack.com
Last fetched
nr.bidderstack.com resolves to 103.75.125.121, announced in 103.75.125.0/24 by FORNEX-NL-AS - Fornex Hosting S.L. in NL. nr.bidderstack.com 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
- 103.75.125.121
103.75.125.0/24 · FORNEX-NL-AS - Fornex Hosting S.L. · Rotterdam, NL
- 103.75.125.122
103.75.125.0/24 · FORNEX-NL-AS - Fornex Hosting S.L. · Rotterdam, NL
- 103.75.125.123
103.75.125.0/24 · FORNEX-NL-AS - Fornex Hosting S.L. · Rotterdam, NL
- 103.75.125.124
103.75.125.0/24 · FORNEX-NL-AS - Fornex Hosting S.L. · Rotterdam, NL
- 103.75.127.14
103.75.127.0/24 · FORNEX-AS - Fornex Hosting S.L. · Frankfurt am Main, DE
- 103.75.127.6
103.75.127.0/24 · FORNEX-AS - Fornex Hosting S.L. · Frankfurt am Main, DE
- 2.58.64.137
2.58.64.0/24 · FORNEX-AS - Fornex Hosting S.L. · Frankfurt am Main, DE
- 2.58.66.194
2.58.66.0/24 · FORNEX-AS - Fornex Hosting S.L. · Frankfurt am Main, DE
- 2.58.67.123
2.58.67.0/24 · FORNEX-AS - Fornex Hosting S.L. · Frankfurt am Main, DE
- 212.2.234.166
212.2.234.0/24 · FORNEX-AS - Fornex Hosting S.L. · Frankfurt am Main, DE
- 212.2.234.174
212.2.234.0/24 · FORNEX-AS - Fornex Hosting S.L. · Frankfurt am Main, DE
- 212.2.234.184
212.2.234.0/24 · FORNEX-AS - Fornex Hosting S.L. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for nr.bidderstack.com is recorded in WhisperGraph.
Attribution
fornex
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for nr.bidderstack.com. 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.
Mail and authentication
Nameservers
- ns1.bidderstack.com
- ns2.bidderstack.com
- ns3.bidderstack.com
Threat-feed evidence
History
Related pages
Pivot from nr.bidderstack.com 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: "nr.bidderstack.com"})-[: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.