Skip to content

Hostname

rodenhiserarchitects.com

Last fetched

rodenhiserarchitects.com resolves to 155.138.255.168, announced in 155.138.240.0/20 by AS-VULTR - The Constant Company, LLC in US. rodenhiserarchitects.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · rodenhiserarchitects.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/rodenhiserarchitects.com

Resolution chain

IPv6 resolution

Attribution

constant

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:228
Registrant organisation
moniker privacy services
Contact emails
0ec0ee05fe856f2b6ed1f86e2ae9f295a19e0a749f0a8e37bdf881f3bc94f191@rodenhiserarchitects.com.whoisproxy.org, 1acbef0d5c65a3f976aee8fc8ae2360c264a1474c86f8e84de680ad94a74dfc6@rodenhiserarchitects.com.whoisproxy.org, 3b7ee77003ecc2107cc5b4bd66700034105135e2a3fd7d0289957e8aead18d02@rodenhiserarchitects.com.whoisproxy.org, 425110499a2b5c389a03afd18e11bd60515c4fb614cff79040279cee07fee3c6@rodenhiserarchitects.com.whoisproxy.org, 4d67c8ca578c31b0bff8a8b4ded4708e35b3766c79cd2dade09c437b4f7644b5@rodenhiserarchitects.com.whoisproxy.org, 51b0e6a241c7546dd9344803689271dc8f3fa1265307152fae0623890f6f3d34@rodenhiserarchitects.com.whoisproxy.org, 5681aab7cd27ea618a21350783151980296582cbe45c5678d203e171461c6a4e@rodenhiserarchitects.com.whoisproxy.org, 5c7352d96218ae35d873d18cfc5f62f5039ce42c4fe24091508ec8754708da36@rodenhiserarchitects.com.whoisproxy.org, 990060ed81158558a7168d41034915f3b5e201d7143fc6865ea7774bdae629a2@rodenhiserarchitects.com.whoisproxy.org, 9e9cbbb43a1760f89bed214d11ff14ce02addc696715e246829440c9ebcf61ad@rodenhiserarchitects.com.whoisproxy.org, bcbeccf64b013c50860343c4670678da2f3991536d3d33fd5743e5daed773ac5@rodenhiserarchitects.com.whoisproxy.org, c6d014575d27e4c8b7d2deba625e9801d20a2904550087b2331087b19432ae85@rodenhiserarchitects.com.whoisproxy.org, cb82d51b15ab7aea047bfd42f70989cc0faa4fec93fb3d7045bb032148d0bf9c@rodenhiserarchitects.com.whoisproxy.org, ced130e7b4ed77c6d581e4c402a058d1458a4c1a80e522f787c073e0a468bdbb@rodenhiserarchitects.com.whoisproxy.org, d470811844a9cbef34fb2142909ad8262990f36393e84f1ff2725aa98028c143@rodenhiserarchitects.com.whoisproxy.org, dffef0da5fb4beeaa7e2440203d5c69a041f4d456e5e012ad5a62794faab1ba7@rodenhiserarchitects.com.whoisproxy.org, ec794fba183adea294aa8f029fe3e4c3ffccc34e6d23f13ad110d3f6e751b94b@rodenhiserarchitects.com.whoisproxy.org, fa8b309390ff54e05b77ea875a4e0be5fac3b0183dc8f249b505bcb4c5ff4f96@rodenhiserarchitects.com.whoisproxy.org

Company

Company
Rodenhiser Architects, LLC
Headquarters
Holliston, United States

Technology

Rodenhiser Architects, LLC has been observed using 22 technologies somewhere in its estate. This is observed use, not an exposure finding. The 20 most widely adopted:

Domain portfolio

Parent company's domain: rodenhiser.com (Rodenhiser)

Subdomains

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

DNSSEC

WhisperGraph records no DNSSEC signature for rodenhiserarchitects.com.

DKIM signing

No DKIM signing vendor is attributed to rodenhiserarchitects.com in WhisperGraph.

Nameservers

  • ns1.tsnameserver.com
  • ns2.tsnameserver.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • rodenhiserarchitects.com

SPF policy

  • a: rodenhiserarchitects.com
  • mx: rodenhiserarchitects.com
  • include: relay.mailchannels.net
  • ip: 103.43.75.180
  • ip: 149.28.255.161
  • ip: 155.138.255.168
  • ip: 18.119.69.218

Threat-feed evidence

History

Related pages

Pivot from rodenhiserarchitects.com into the addresses, networks and registries it depends on.

Queries

This hostname's full card — resolution chain, registration, mail policy, DNSSEC and mail authentication.


MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)-[:RESOLVES_TO]->(ip:IPV4)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap)
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (ip)-[:LOCATED_IN]->(city:CITY)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(ipc:COUNTRY)
WITH h, ip, ap, a, an, city, ipc
LIMIT 20
WITH h,
     collect({ip: ip.name, prefix: ap.name, asn: a.name, network: an.name, city: city.name, country: ipc.name}) AS resolutions,
     collect(a.name) AS asnNames,
     collect(ap.name) AS prefixNames,
     collect(ap.isMoas) AS moasFlags,
     collect(ap.rpkiStatus) AS rpkiStatuses,
     head(collect(a)) AS primaryAsn,
     head(collect(ap)) AS primaryPrefix
OPTIONAL MATCH (primaryPrefix)-[:CONFLICTS_WITH]->(conflict:ASN)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn,
     collect(conflict.name) AS conflictAsns
OPTIONAL MATCH (h)-[:HAS_REGISTRAR]->(reg:REGISTRAR)
OPTIONAL MATCH (h)-[:REGISTERED_BY]->(org:ORGANIZATION)
OPTIONAL MATCH (h)-[:CHILD_OF]->(tld:TLD)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
     collect(reg.name) AS registrars,
     collect(org.name) AS organizations,
     collect(tld.name) AS tlds
OPTIONAL MATCH (h)-[:HAS_EMAIL]->(em:EMAIL)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
     registrars, organizations, tlds,
     collect(em.name) AS emails
OPTIONAL MATCH (h)-[:HAS_PHONE]->(ph:PHONE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
     registrars, organizations, tlds, emails,
     count(ph) AS phoneCount
OPTIONAL MATCH (h)<-[:MAIL_FOR]-(mx:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
     registrars, organizations, tlds, emails, phoneCount,
     collect(mx.name)[0..20] AS mxHosts
OPTIONAL MATCH (h)<-[:NAMESERVER_FOR]-(ns:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
     registrars, organizations, tlds, emails, phoneCount, mxHosts,
     collect(ns.name) AS nameservers
OPTIONAL MATCH (h)-[spf:SPF_A|SPF_EXISTS|SPF_INCLUDE|SPF_IP|SPF_MX|SPF_REDIRECT]->(spfTarget)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
     registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers,
     collect({mechanism: type(spf), target: spfTarget.name})[0..50] AS spf
OPTIONAL MATCH (h)-[:SIGNED_WITH]->(alg:DNSSEC_ALGORITHM)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
     registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
     collect(alg.name) AS dnssecAlgorithms
OPTIONAL MATCH (h)-[:DMARC_REPORTS_TO]->(dm:DMARC_RECIPIENT)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
     registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
     collect(dm.name)[0..5] AS dmarcRecipients
OPTIONAL MATCH (h)-[:DKIM_SIGNED_BY]->(dk:VENDOR)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
     registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
     dmarcRecipients,
     collect(coalesce(dk.displayName, dk.name))[0..5] AS dkimVendors
OPTIONAL MATCH (h)-[:HAS_SIGNAL]->(hs:THREAT_SIGNAL_TYPE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
     registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
     dmarcRecipients, dkimVendors,
     collect(hs.name) AS dnsSignals
CALL { WITH primaryAsn MATCH (primaryAsn)-[:BGP_NEIGHBOR]-(peer:ASN) RETURN count(peer) AS asnPeerCount }
RETURN h.name AS name,
       h.rank AS rank,
       h.verdictLevel AS verdictLevel,
       h.verdictScore AS verdictScore,
       h.verdictBlocking AS verdictBlocking,
       h.verdictCoverage AS verdictCoverage,
       h.verdictAdvisory AS verdictAdvisory,
       h.threatSources AS threatSources,
       h.threatFirstSeen AS threatFirstSeen,
       h.threatLastSeen AS threatLastSeen,
       h.isTor AS isTor,
       h.isVpn AS isVpn,
       h.isProxy AS isProxy,
       h.isC2 AS isC2,
       h.isPhishing AS isPhishing,
       resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, conflictAsns,
       registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
       dnssecAlgorithms, dmarcRecipients, dkimVendors, dnsSignals,
       h.companyName AS companyName,
       h.companyIndustry AS companyIndustry,
       h.companyHqCountry AS companyHqCountry,
       h.companyHqCity AS companyHqCity,
       asnPeerCount
Run yourself →

The observed subdomain count, to depth 3.


MATCH (h:HOSTNAME {name: $host})
CALL { WITH h MATCH (h)<-[:CHILD_OF*1..3]-(sub:HOSTNAME) RETURN count(sub) AS subdomainCount }
RETURN subdomainCount
Run yourself →

Technologies the company behind this domain has been observed running, most widely adopted first.


MATCH (:HOSTNAME {name: $host})-[:RUNS_TECHNOLOGY]->(t:TECHNOLOGY)
WITH t.name AS name, t.category AS category, t.adopterCount AS adopters
ORDER BY adopters DESC, name
WITH collect({name: name, category: category}) AS technologies, count(*) AS total
RETURN total, technologies[0..20] AS technologies
Run yourself →

Peer companies (outbound SIMILAR_TO).

MATCH (:HOSTNAME {name: $host})-[:SIMILAR_TO]->(peer:HOSTNAME) RETURN peer.name AS host ORDER BY host LIMIT 8
Run yourself →

The parent company's domain and this company's domain portfolio (PARENT_OF).


MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)<-[:PARENT_OF]-(parent:HOSTNAME)
WITH h, collect({host: parent.name, company: parent.companyName})[0..3] AS parents
OPTIONAL MATCH (h)-[:PARENT_OF]->(child:HOSTNAME)
RETURN parents, collect({host: child.name, company: child.companyName})[0..10] AS portfolio
Run yourself →

Or query Whisper from your own LLM workflow via the Whisper MCP server.